anaconda/f35 — English @ Fedora Weblate: Workarounds for manual installations: * Select only the disks with …

Source string Source string

English

Workarounds for manual installations:
* Select only the disks with the same sector size during manual installation in graphical or text mode.
* When disks with inconsistent sector size are selected for the installation, restrict each created LVM Volume Group to use Physical Volumes with the same sector size. This can only be done in graphical mode in the Custom partitioning spoke.

Workarounds for kickstart installations:
* Restrict what disks are used for the partitioning by specifying 'ignoredisk --drives=..' or 'ignoredisk --only-use=..'.
* Specify what disks should be used for each created LVM Physical Volume: partition pv.1 --ondisk=..'.

General workarounds:
* Plain partitioning scheme can be used instead of LVM.
* Some drives support re-configuration of sector sizes, for example by running 'hdparm --set-sector-size=<SIZE> <DEVICE>'.

Needs editing

The string is read only.

Skip

	English	Actions
	No volume group exists with the name "{}". Specify volume groups before logical volumes.
	Cache PVs must belong to the same VG as the cached LV
	No thin pool exists with the name "{}". Specify thin pools before thin volumes.
	logvol --noformat must also use the --name= option.
	Logical volume "{}" given in logvol command does not exist.
	Logical volume name "{}" is already in use in volume group "{}".
	Logical volume size "{}" must be larger than the volume group extent size of "{}".
	Btrfs partition "{}" has a format of "{}", but should have a format of "btrfs".
	Tried to use undefined partition "{}" in Btrfs volume specification.
	Btrfs volume defined without any member devices. Either specify member devices or use --useexisting.
	Btrfs volume "{}" specified with --useexisting does not exist.
	The size "{}" is invalid.
	The mount point "{}" is not valid. It must start with a /.
	Target size "{size}" for device "{device}" is invalid.
	Failed to proceed with the installation.
	Workarounds for manual installations: * Select only the disks with the same sector size during manual installation in graphical or text mode. * When disks with inconsistent sector size are selected for the installation, restrict each created LVM Volume Group to use Physical Volumes with the same sector size. This can only be done in graphical mode in the Custom partitioning spoke. Workarounds for kickstart installations: * Restrict what disks are used for the partitioning by specifying 'ignoredisk --drives=..' or 'ignoredisk --only-use=..'. * Specify what disks should be used for each created LVM Physical Volume: partition pv.1 --ondisk=..'. General workarounds: * Plain partitioning scheme can be used instead of LVM. * Some drives support re-configuration of sector sizes, for example by running 'hdparm --set-sector-size=<SIZE> <DEVICE>'.
	File system type "{}" given in autopart command is invalid.
	Btrfs file system is not supported.
	Disklabel "{}" given in clearpart command is not supported on this platform.
	Disk "{}" given in clearpart command does not exist.
	Device "{}" given in clearpart device list does not exist.
	Disk "{}" given in ignoredisk command does not exist.
	NIC "{}" given in fcoe command does not exist.
	Network interface "{nic}" required by iSCSI "{iscsi_target}" target is not up.
	iscsi --iface must be specified (binding used) either for all targets or for none
	Namespace "{}" given in nvdimm command was not found.
	Disk "{}" given in nvdimm command does not exist.
	Incorrectly specified origin of the snapshot. Use format "VolGroup/LV-name"
	Unable to find /bin/bash to execute! Not starting shell.
	Rescue
	The rescue environment will now attempt to find your Linux installation and mount it under the directory : %s. You can then make any changes required to your system. Choose '1' to proceed with this step. You can choose to mount your file systems read-only instead of read-write by choosing '2'. If for some reason this process does not work choose '3' to skip directly to a shell.

Loading…

vladimirslavik

Comment added

Yes, it's exactly as you guess.

2 years ago

alciregi

Comment added

I think so

2 years ago

atriwidada

Comment added

does this line * Specify what disks should be used for each created LVM Physical Volume: partition pv.1 --ondisk=..'. missing opening quote? * Specify what disks should be used for each created LVM Physical Volume: 'partition pv.1 --ondisk=..'.

2 years ago

Browse all string changes

atriwidada

Source string comment

2 years ago

alciregi

Source string comment

I think so

2 years ago

vladimirslavik

Source string comment

Yes, it's exactly as you guess.

2 years ago

Things to check

Comments

There are 3 unresolved comments for this string.

View

Glossary

English	English
No related strings found in the glossary.

String information

Flags

read-only

Source string location

pyanaconda/modules/storage/constants.py:30

String age

2 years ago

Last updated

11 months ago

Source string age

2 years ago

Translation file

f35/anaconda.pot, string 741